Skip to content

fix(modal): add icon status style #3504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 17, 2025
Merged

fix(modal): add icon status style #3504

merged 1 commit into from
Jun 17, 2025

Conversation

James-9696
Copy link
Collaborator

@James-9696 James-9696 commented Jun 13, 2025

PR

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our Commit Message Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • Style
    • Updated the mobile status icon in the modal component to have a consistent size and improved color coding based on status, matching the appearance of the desktop version.

Copy link

coderabbitai bot commented Jun 13, 2025

Walkthrough

The update refines the CSS classes for the mobile status icon in the modal component. It explicitly sets the icon's height and width, and adds conditional color classes based on the status prop, aligning the mobile icon's appearance with the desktop version. No exported or public entity declarations are changed.

Changes

File(s) Change Summary
packages/vue/src/modal/src/mobile-first.vue Updated status icon CSS classes: added explicit sizing and conditional color classes per status.

Suggested labels

bug

Poem

A rabbit hopped in with a brush so fine,
Tweaking icons to perfectly align.
Now colors and sizes are just right—
Mobile and desktop, both a delight!
With every hop and every hue,
The modal shines, refreshed and new.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/vue/src/modal/src/mobile-first.vue

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the bug Something isn't working label Jun 13, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1490dcd and 2e1e603.

📒 Files selected for processing (1)
  • packages/vue/src/modal/src/mobile-first.vue (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR E2E Test (pnpm test:e2e3)

Comment on lines +364 to +369
'h-4 w-4 inline-block sm:hidden mr-1.5 fill-current',
type === 'message' ? 'w-5 h-5 self-center shrink-0' : 'h-6 w-auto',
{ 'text-color-success': status === 'success' },
{ 'text-color-info-secondary': ['info', 'question'].includes(status) },
{ 'text-color-warning': status === 'warning' },
{ 'text-color-error': status === 'error' }
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Status-matching is case-sensitive → colour classes silently break when status is upper-case

statusIcon / mobileStatusIcon are resolved with status.toUpperCase(), but the colour classes still compare against lower-case literals ('success', 'warning', …).
If the caller passes 'SUCCESS' or 'Warning', the icon shows up, yet the colour class is not applied – an easy-to-miss visual bug.

Refactor once so both the icon mapping and colour classes use the same normalised value; it also removes the duplication between desktop & mobile blocks.

@@
-      status,
+      // normalise status once for icon mapping & CSS utility checks
+      status,
+      statusUpper = typeof status === 'string' ? status.toUpperCase() : '',
+      statusLower = typeof status === 'string' ? status.toLowerCase() : '',
@@
-    const statusIcon = typeof status === 'string' ? STATUS_MAPPING_COMPINENT[status.toUpperCase()] : status
-    const mobileStatusIcon = typeof status === 'string' ? MOBILE_STATUS_MAPPING_COMPINENT[status.toUpperCase()] : status
+    const statusIcon =
+      typeof status === 'string' ? STATUS_MAPPING_COMPINENT[statusUpper] : status
+    const mobileStatusIcon =
+      typeof status === 'string' ? MOBILE_STATUS_MAPPING_COMPINENT[statusUpper] : status
@@
-                                    { 'text-color-success': status === 'success' },
-                                    { 'text-color-info-secondary': ['info', 'question'].includes(status) },
-                                    { 'text-color-warning': status === 'warning' },
-                                    { 'text-color-error': status === 'error' }
+                                    { 'text-color-success': statusLower === 'success' },
+                                    { 'text-color-info-secondary': ['info', 'question'].includes(statusLower) },
+                                    { 'text-color-warning': statusLower === 'warning' },
+                                    { 'text-color-error': statusLower === 'error' }

This keeps behaviour unchanged for correctly-cased inputs while fixing upper-/mixed-case ones and DRYs up the comparisons.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In packages/vue/src/modal/src/mobile-first.vue around lines 364 to 369, the
status string is compared in a case-sensitive way for applying colour classes,
causing issues when status is upper- or mixed-case. Normalize the status value
to a consistent case (e.g., lowercase) once before these comparisons and use
this normalized value both for icon resolution and colour class conditions. This
will fix the colour class application for all case variations and reduce
duplication between desktop and mobile icon handling.

@zzcr zzcr merged commit f7cac5e into dev Jun 17, 2025
9 of 11 checks passed
@zzcr zzcr deleted the fix-modal-we branch June 17, 2025 01:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants